JavaScript or API integration

Overview

Once you have decided whether your integration will be done Server side or Client side, the next decision to be made will be which method of implementation you will use. Client Side sites can choose between JSON or API. Meanwhile, Server-side sites are limited to using APIs.

Understanding the way each of the two implementation methods works is important, no matter which product or products from the ADA lineup you are implementing.

Retailers will want to work closely with their ADA team to get the most out of their implementation. While many features are self-service, taking advantage of the RR team and the training provided will help avoid hiccups in implementation.

When a customer visits a site that uses a ADA product, the site sends information about the customer and the site to the Digital Experience Personalization and receives personalized content in return. This call to the Digital Experience Personalization and the response can be made from the customer’s browser (which we call a client-side request) or from the merchant’s server (a server-side request).

JavaScript Integration

When using a client-side integration, you can take advantage of our JavaScript integration, which gives you a good feature not yet available with API calls:

  • Access to additional debugging and testing tools.

API

Both client-side and server-side sites can use API calls to communicate with the Digital Experience Personalization server.

The API calls are documented in detail in both this core integration category as well as in product specific locations for product specific features.

Best Practice for Placement Requests

In some cases, deviations may be necessary, but our recommended best practice is to consolidate all placement requests within a single submission. This approach offers several benefits:

Automatic Deduplication: Products are automatically deduplicated across all placements included in a single request.

Optimized Strategy Allocation: Experience Optimizer applies distinct strategies to each placement within the same request.

Enhanced Reporting Accuracy: Consolidated placement requests lead to more accurate view counts in reporting.

Simplified Maintenance of RCS Values: Managing RCS (RichRelevance Client Session) values is more straightforward when requests are consolidated.

For more information about RCS see, Integrating RR cookies for RecsForPlacements